Evil Flowerchild
   |
Posted - 2008.11.15 16:09:00 -
[1]
Edited by: Evil Flowerchild on 15/11/2008 16:12:08
 Originally by: Scagga Laebetrovo
Edited by: Scagga Laebetrovo on 15/11/2008 11:12:51
There is a significant bug I've faced with Blockade runners, that cost me approximately 700m. This is the scenario I had with my prowler:
Warp to gate while cloaked with cov ops cloak
Gate is camped, I jump through and find a broadsword waiting
No problem, I've got a cov ops cloak right?
I break cloak to align, while also hitting the cov ops cloak
I'm given a message when I click the cov ops cloak, roughly like "re-activating after previous activation, 5 seconds". I'm a sitting duck.
Broadsword catches me
I burn back to the gate and get away. The cloak works when I jump to the other side.
Ok, I try this again. Same thing happens, I'm told there is a reactivation delay. However, this time I can't burn back to the gate, because the broadsword brought his buddies. I lose a blockade runner and 280 warp scramblers bought at 1-1.4m, as well as my implants set since for some reason the only session change I got to see was appearing in the cloning bay...
Right. This has never, ever happened with any other ship I've used a cov ops cloak on. I have extensive experience with recons and covert ops ships. There has never been a 30 second reactivation delay, nor a delay that persists after jumping. This was not mentioned in the patch notes.
I've petitioned this 3 days ago, and am extremely unsatisfied with how it's being handled. First it is said that they have strict reimbursement policies and that they don't have this error happening to them so it's probably not a game defect (some consolation eh?) , the bug only happens to me then?), then they say they can't trust the logs that I've provided - do their logs have a different story?
If you've ever shown info on the cov-ops cloaking device you will see under its attributes that there is a 30 second activation delay. This has always been there and why it wasn't listed in the patch notes.
The reason this never happened on cov-ops and recon ships is they have a bonus to reduce the delay by 90% that isn't listed, blockade runners do not get this bonus. So no bugs and everything is working as intended.
It is unlikely you will get reimbursed for your oversight on reading module attributes and not testing the new ship out before taking an expensive load into hostile territory. |